Conversation
|
@AllenChangMusic @jiggs82 please test the lates CI of current branch to see if the support of Android 17 beta 3 is complete now. |
Vector release build still isn't working for me, on lsposed manager says it's not installed |
|
@jiggs82 Please provide logs by uploading the folder |
|
@jiggs82 It seems that Vector CI build is not flashed correctly. |
|
@JingMatrix debug build works, but release build does not Also... Looks like Vector has issues enabling new modules. And if you uninstall it, and reinstall, you aren't able to enable any modules. May be related to the report in the other thread where it isn't able to create the lspd folder |
Still same issues and yes now I encounter that :( |
|
There are bugs in the refactoring, hence I create pr #603 to fix the issue for the java code before refactoring, to help isolated issues. |
|
When I use the release build, it crashes, but the debug build works fine. |
3611782 to
0da27d9
Compare
|
@jiggs82 @AllenChangMusic @mmmpipi Please also test the latest CI builds of current branch, before I finally merge it. |
Tested and one module - InstaEclipse doesn't work in this version, but did in the previous CI. One thing to note is in LSPosed manager, it keeps complaining there's an update, but it's the old pre-vector version |
|
@AllenChangMusic Please upload your debug version logs for the module not working. |
|
@JingMatrix I'm not seeing any specific crash log, but this CI causes IG to crash |
|
@AllenChangMusic I see logs of containing |
Instagram app just crashes, won't even open. Compared to the previous CI, it opens fine, and you can open the InstaEclipse settings (long holding the search icon in the instagram app), and use the app just fine |
Flashed latest build and all good here 👍🏻 |
|
@JingMatrix anything you need me to debug or send logs for to help troubleshoot why it's causing crashing? |
|
@AllenChangMusic I think it is a problem of the module. |
Hi, I am the dev of InstaEclipse, this issue was fixed with InstaEclipse 0.5 debug, the user is using it. I will check myself... Thanks for the great LSPosed/LSPatch!! |
|
@ReSo7200 Nice to hear from you, and it is my pleasure to serve the community. Please do tell me if current refactoring (this pr) is causing issues for your module. I will wait for your test result before merging this. |
|
@ReSo7200 Looking through logcat, seeing these 3 errors consistently popping up, not sure if it's related to the hooking.
|
it works fine! thanks |
|
@bikram-agarwal Please if the latest CI build from current pr works for you. |
No, modules tab is again blank when I flash this. |
|
@CoelacanthusHex Please test the build https://github.com/JingMatrix/Vector/actions/runs/23852214655, I think it should be working this time. |
Yeah. It works fine now! |
|
CI build 3029 is working good for me as well. |
|
@Dev4Mod @huynhbaman @AbdulrahmanAlamodi @Things22 Current PR is going to be merged, and I would like to know if it is working for you. |
|
Quick note: CliHandler.kt has an "rm" (remove module from scope) case in handleScope, but Cli.kt is missing the associated command. And one more question: did you remove the backup/restore feature via the CLI? |
Starting with Android 17 Beta 3 (detected in framework.jar, though not yet published to AOSP), the internal API for XmlUtils has changed its method signature. Specifically, the return type of readMapXml was modified from HashMap to the more generic Map interface. Old signature: ``` Lcom/android/internal/util/XmlUtils;->readMapXml(Ljava/io/InputStream;)Ljava/util/HashMap; ``` New signature: ``` Lcom/android/internal/util/XmlUtils;->readMapXml(Ljava/io/InputStream;)Ljava/util/Map; `` We migrate the call to use reflection.
|
@AnatolyJacobs I think the easiest backup / restore method is simply back up the folder |
|
@JingMatrix I asked those who use the CLI. Yes, this feature is very useful when configuring multiple devices. In any case, the decision is yours. |
|
@AnatolyJacobs I have added the Regarding the |
|
@JingMatrix Yes, full backup/restore now works. Thanks a lot! |
- Replace `fprintf` with `writev` (scatter-gather I/O) for atomic, zero-copy writes. - Optimize tag filtering using binary search and `std::string_view` on the hot path.
Xposed module Thanox is built with both legacy and libxposed API, we prefer the former as it is more stable. Moreover, fix function isRunningManager and logging
In WAE it works almost perfectly, only something strange is happening. The system hook isn't working properly. The core patch, despite not showing any errors, doesn't allow app downgrading, even though it worked fine before the project migrated to Vector. |
I just use 2 xposed module, Corepatch and RevanceXposed. On newest CI, Revance work good, but corepatch failure |





This PR transitions the framework daemon from legacy Java to a modernized Kotlin implementation, rebranded as
Vector. The refactor moves beyond a literal translation to implement a more robust, domain-driven architecture.See REAMDE in module
daemonfor more implementation details.